-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Hotfix az rewrite and storage_preview #1075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR: |
|
|
||
| # TODO migrate to public azdev | ||
| echo "Running linter..." | ||
| # azdev cli-lint --ci --extensions $ext |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we run the azdev linter and azdev verify load-all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, the public azdev doesn't have those two commands. So it's a dangerous hotfix which will open the Pandora Box that leave extension commands without some correctness verification.
…re#1075 (Azure#1082) * [azdev] Upgrade linter to the public azdev mentioned at hotfix PR Azure#1075 * Optimize readability
WARNING: This hotfix comments out
azdev verify load-allandazdev cli-linter(from azure-cli) , which opens the Pandora box that leave extension commands without some correctness verification. Will migrate those function into the public azure-cli-dev-tools ASAP.This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?For new extensions: